cmake: Set the release/debug based on Kconfig #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use the Zephyr KConfig `CONFIG_DEBUG` to determine if the Rust code should be built as release or debug. This will better optimize the code. Applications can still set options for `[profile.release]` to enable things such as run time assertions. For example, debug symbols can still be enabled with `debug = "full"`, which attempts to insert debugging information, although the optimizer can still make the code challenging to debug.o `debug-assertions = true`, and `overflow-checks = true` can still be enabled in the release builds, for some additional checks. Signed-off-by: David Brown <[email protected]>
Ablu
approved these changes
Dec 5, 2024
cfriedt
approved these changes
Dec 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the Zephyr KConfig
CONFIG_DEBUGto determine if the Rust code should be built as release or debug. This will better optimize the code.Applications can still set options for
[profile.release]to enable things such as run time assertions. For example, debug symbols can still be enabled withdebug = "full", which attempts to insert debugging information, although the optimizer can still make the code challenging to debug.odebug-assertions = true, andoverflow-checks = truecan still be enabled in the release builds, for some additional checks.